<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN""http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="zh" xml:lang="zh" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<head>
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Task Descriptor: Develop Development Case</title>
<meta name="uma.type" content="TaskDescriptor">
<meta name="uma.name" content="develop_development_case">
<meta name="uma.presentationName" content="Develop Development Case">
<meta name="uma.guid" content="_gnaptEoeEdqrjq4i3fchvA">
<meta name="element_type" content="TaskDescriptor">
<meta name="filetype" content="description">
<meta name="role" content="">
<link rel="StyleSheet" href="./../../css/default.css" type="text/css">
<script src="./../../scripts/ContentPageResource.js" type="text/javascript" language="JavaScript"></script><script src="./../../scripts/ContentPageSection.js" type="text/javascript" language="JavaScript"></script><script src="./../../scripts/ContentPageSubSection.js" type="text/javascript" language="JavaScript"></script><script src="./../../scripts/ActivityTreeTable.js" type="text/javascript" language="JavaScript"></script><script src="./../../scripts/ProcessElementPage.js" type="text/javascript" language="JavaScript"></script><script src="./../../scripts/ContentPageToolbar.js" type="text/javascript" language="JavaScript"></script><script src="./../../scripts/contentPage.js" type="text/javascript" language="JavaScript"></script><script src="./../../scripts/processElementData.js" type="text/javascript" language="JavaScript"></script><script type="text/javascript" language="JavaScript">
					var defaultQueryStr = '?proc={659D51DD-DF1F-465E-9F3A-2FC6F9BC7C34}&path={659D51DD-DF1F-465E-9F3A-2FC6F9BC7C34},{37A50EF5-CC73-4E38-B851-997879548110},_gnaptEoeEdqrjq4i3fchvA';
					var backPath = './../../';
					var imgPath = './../../images/';
					var nodeInfo=null;
					contentPage.preload(imgPath, backPath, nodeInfo, defaultQueryStr, true, true, false);
				</script>
</head>
<body>
<div id="breadcrumbs"></div>
<table border="0" cellpadding="0" cellspacing="0" width="100%">
<tr>
<td valign="top">
<div id="page-guid" value="_gnaptEoeEdqrjq4i3fchvA"></div>
<table border="0" cellspacing="0" cellpadding="0" width="100%">
<tr>
<td class="pageTitle" nowrap="true">Task Descriptor: Develop Development Case</td><td width="100%">
<div align="right" id="contentPageToolbar"></div>
</td><td width="100%" class="expandCollapseLink" align="right"><a name="mainIndex" href="./../../index.htm"></a><script language="JavaScript" type="text/javascript" src="./../../scripts/treebrowser.js"></script></td>
</tr>
</table>
<table width="100%" border="0" cellpadding="0" cellspacing="0">
<tr>
<td class="pageTitleSeparator"><img src="./../../images/shim.gif" alt="" title="" height="1"></td>
</tr>
</table>
<div class="overview">
<table width="97%" border="0" cellspacing="0" cellpadding="0">
<tr>
<td width="50"><img src="./../../images/taskdes_lg_dgm32.gif" alt="" title=""></td><td>
<table class="overviewTable" border="0" cellspacing="0" cellpadding="0">
<tr>
<td valign="top">This task describes how to create a Development Case that describes the software-development process for an organization or a project.</td>
</tr>
<tr>
<td>Based on Method Task: <a href="./../../rup/tasks/develop_development_case_B10E3391.html" guid="{F6999E01-701F-4D48-9E83-A063CB35912B}">Develop Development Case</a></td>
</tr>
</table>
</td>
</tr>
</table>
</div>
<div class="sectionHeading">Relationships</div>
<div class="sectionContent">
<table class="sectionTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<th class="sectionTableHeading" scope="row">Roles</th><td class="sectionTableCell" width="30%"><span class="sectionTableCellHeading">Main:
								</span>
<ul>
<li>
<a href="./../../rup/capabilitypatterns/rup_process_engineer_A7A8881E.html" guid="_CdDjFhi2Edq_uI8xTPML6g">流程工程师</a>
</li>
</ul>
</td><td class="sectionTableCell" width="30%"><span class="sectionTableCellHeading">Additional:
								</span></td><td class="sectionTableCell"><span class="sectionTableCellHeading">Assisting:
								</span></td>
</tr>
<tr valign="top">
<th class="sectionTableHeading" scope="row">Inputs</th><td class="sectionTableCell" width="30%"><span class="sectionTableCellHeading">Mandatory:
								</span>
<ul>
<li>None</li>
</ul>
</td><td class="sectionTableCell" width="30%"><span class="sectionTableCellHeading">Optional:
								</span>
<ul>
<li>
<a href="./../../rup/capabilitypatterns/rup_development_case_E316A5FF.html" guid="_CdDjEhi2Edq_uI8xTPML6g">开发案例</a>
</li>
<li>
<a href="./../../rup/capabilitypatterns/rup_project_plan_90D57BFF.html" guid="_gngwQEoeEdqrjq4i3fchvA">软件开发计划</a>
</li>
</ul>
</td><td class="sectionTableCell"><span class="sectionTableCellHeading">External:
								</span>
<ul>
<li>None</li>
</ul>
</td>
</tr>
<tr valign="top">
<th class="sectionTableHeading" scope="row">Outputs</th><td class="sectionTableCell" colspan="3">
<ul>
<li>
<a href="./../../rup/capabilitypatterns/rup_development_case_E316A5FF.html" guid="_CdDjEhi2Edq_uI8xTPML6g">开发案例</a>
</li>
</ul>
</td>
</tr>
</table>
</div>
<div class="sectionHeading">Steps</div>
<div class="sectionContent">
<table class="sectionTable" border="0" cellspacing="0" cellpadding="0">
<tr>
<td class="sectionTableCell">
<div class="stepHeading">Decide How to Perform Each Discipline </div>
<div class="stepContent">
<table class="stepTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<td><a id="PerformDisciplines" name="PerformDisciplines"></a> 
<p>
    Part of tailoring the NUP framework for use on a specific project is to decide on which disciplines to introduce. As
    described in <a class="elementLinkWithType" href="./../../rup/tasks/tailor_process_for_project_6CFD05E2.html" guid="{1BA9AAA0-DA89-4C14-B45A-CE28A8A10894}">Task: 为项目定制开发流程</a> , you should avoid using all of NUP in one single
    project. And if your project is fairly new to the practices described in the NUP, you should concentrate on limiting
    the number of unknown factors to a handful, to ease the transition of the teams onto a new process platform.
</p>
<p>
    Once you have decided which disciplines you need to introduce, decide the following for each:&nbsp;
</p>
<ul>
    <li>
        How to perform the workflow.&nbsp;
    </li>
    <li>
        Which parts of the workflow should be used.&nbsp;
    </li>
    <li>
        When, during the project's lifecycle, to introduce the workflows and their parts.&nbsp;
    </li>
</ul>
<p>
    To help you decide, guidelines have been developed for each discipline called "Important Decisions in &lt;Discipline
    X&gt;. In these guidelines, there are is a section called "Decide How to Perform the Workflow".&nbsp; See the attached
    guidelines for the disciplines included in this configuration.
</p>
<p>
    When you consider introducing a particular discipline, or part of one, take the following into account:
</p>
<ul>
    <li>
        <b>Applicability</b>. Is it applicable for the project? Does it really add value to introduce it?
    </li>
    <li>
        <b>Problems and root causes addressed</b>. Does it address any of the perceived problems and their root causes?
    </li>
    <li>
        <b>Tool support</b>. What tool support is needed?
    </li>
    <li>
        <b>Timing</b>. When during the project's lifecycle should it be introduced? See <a class="elementLinkWithType" href="./../../rup/guidances/concepts/implementing_a_process_in_a_project_3656F98A.html" guid="2.870714010568015E-306">Concept: 在项目中实现流程</a>, for more information.
    </li>
    <li>
        <b>Cost of implementing</b>. What is the cost of implementing it in the project? This includes: 
        <ul>
            <li>
                Cost to train project members.&nbsp;
            </li>
            <li>
                Cost to install the supporting tools.
            </li>
            <li>
                Cost to develop guidelines and templates.
            </li>
        </ul>
    </li>
</ul></td>
</tr>
</table>
</div>
<div class="stepHeading">Tailor Artifacts per Discipline </div>
<div class="stepContent">
<table class="stepTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<td><a id="TailorArtifacts" name="TailorArtifacts"></a> 
<p>
    Select the right set of work products for the project to produce.&nbsp;If you cannot clearly articulate why the work
    product should be produced, for example if no external stakeholder has requested it, then consider excluding it.
</p>
<p>
    It is a good practice to use the development case to document any deviations from the underlying process, so exclusion
    of any work product should be justified and documented.
</p>
<p>
    Perform the following steps:
</p>
<ol>
    <li>
        Decide how the work product (modeling element or document) should be used.&nbsp; For information on
        a&nbsp;classification scheme for documenting the importance of individual work products and whether or not they
        will be used, see <a class="elementLinkWithType" href="./../../rup/guidances/guidelines/classifying_work_products_4250A298.html" guid="7.27749388241665E-306">Guideline: 将工作产品分类</a>.
    </li>
    <li>
        Decide the review level for each work product and capture it in the "Review Details". For details see <a class="elementLinkWithType" href="./../../rup/guidances/guidelines/review_levels_72ACB304.html" guid="8.546224914239529E-306">Guideline: 评审级别</a>. Decide how to review each work product; that is, which review
        procedures to use.&nbsp;
    </li>
    <li>
        Decide how you should capture the final results of a discipline. Do you need to store the results on paper? If so,
        you have to decide on one or several reports that extract the results from the tools, and capture the results on
        paper.&nbsp;
    </li>
    <li>
        Decide which tools to use to develop and maintain the work product.
    </li>
    <li>
        Decide which properties to use and how to use them. See the Properties table for each work product and the section
        titled "Tailoring" of each work product.
    </li>
    <li>
        When relevant, decide which stereotypes to use. For each work product, see the section titled "Tailoring."
    </li>
    <li>
        Decide on an outline for the document work products. For the respective work product, see the "Brief Outline."
        portion of the main description.
    </li>
</ol>
<p>
    In addition to these steps you should also:
</p>
<ul>
    <li>
        Decide which reports to use. Decide if you need any work reports to extract information from models, then document
        the information on paper for reviews. These work reports are usually treated as casual since they are temporary and
        will be discarded as soon as the review is complete. You may need to tailor the outline.
    </li>
</ul>
<p>
    There are more things to decide for each discipline. See the "important decisions in &lt;discipline name&gt;"
    guidelines for each discipline for more details.
</p></td>
</tr>
</table>
</div>
<div class="stepHeading">Tailor Tasks per Discipline</div>
<div class="stepContent">
<table class="stepTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<td><a id="ModifyDisciplines" name="ModifyDisciplines"></a> 
<p>
    Study the modified set of work products and the tasks that use, create and update these work products. Decide whether
    you should modify or simplify these tasks. Note that for each task input and output work products are indicated. Be
    sure to delete any unnecessary step or task. Consider the following:
</p>
<ul>
    <li>
        Introduce new steps and possibly new tasks to reflects the work products, reports, and documents that you have had
        to add.
    </li>
    <li>
        Examine how the tools used can facilitate, automate, or even suppress some of the steps.
    </li>
    <li>
        Introduce into the tasks any specific guidelines and rules inherited from the organization's experience. They may
        be added as guidance points, checklists, review items, or left as separate documents that can be referenced.
    </li>
    <li>
        Once the tasks are known, review the workflows associated with each discipline that show how tasks interplay,
        removing or adding tasks as necessary.
    </li>
    <li>
        Whole disciplines can be omitted or created.
    </li>
    <li>
        You may have to introduce some additional roles to take care of special tasks requiring specific skills.
    </li>
</ul>
<p>
    Describe the changes in the Development Case.
</p></td>
</tr>
</table>
</div>
<div class="stepHeading">Choose Lifecycle Model </div>
<div class="stepContent">
<table class="stepTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<td><a id="ChooseLifecycleModel" name="ChooseLifecycleModel"></a> 
<p>
    Choose the kind of lifecycle model the project should employ. Refine the NUP model and adjust milestones and the
    milestone evaluation criteria if necessary. You may even decide to omit one or several of the phases, or add or remove
    milestones. See <a class="elementLinkWithType" href="./../../base_concepts/guidances/concepts/phase_85B003C3.html" guid="__7xOEC7aEdqHMdmRzC0-2g">Concept: 阶段 </a> &nbsp;and <a class="elementLinkWithType" href="./../../base_concepts/guidances/concepts/iteration_441A13D7.html" guid="3.379871268737602E-305">Concept: 迭代</a>
    for more information and ideas. Document the project's lifecycle model in section "Overview of the Development Case" of
    the Development Case.
</p>
<p>
    In addition to selecting the&nbsp;overall lifecycle model, it is also important to decide <em>how</em> to perform the
    discipline workflows (what activities to perform and in what order), as well as to decide <em>when</em>, during that
    project lifecycle, to introduce each part of the disciplines' workflow.&nbsp; For information on how to tailor the
    workflow for each of the NUP disciplines, see the usage notes for the reference workflows provided for each NUP
    discipline. Document the discipline workflow decisions in the Development Case.
</p></td>
</tr>
</table>
</div>
<div class="stepHeading">Describe Sample Iterations </div>
<div class="stepContent">
<table class="stepTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<td><a id="DescribeIterationWorkflows" name="DescribeIterationWorkflows"></a> 
<p>
    Describe at least one sample iteration (more likely you will describe several) for each phase. These iteration
    descriptions describe how the project will work in different iterations and phases of the project. See the different
    phase descriptions under the <a class="elementLink" href="./../../rup/customcategories/rup_lifecycle_100BF298.html" guid="_PEpmMCVuEdqSZ9OimJ-AzA">NUP 生命周期</a>&nbsp;page for detailed examples.
</p>
<p>
    The purpose of describing sample iterations in the development case is to communicate to the project teams, which tasks
    your project will perform, and in which order. As such it can serve as a more detailed iteration plan. The description
    of the sample iterations should be brief. Do not include details that belong in the tasks, work products and
    guidelines. You can choose to describe the sample iterations in terms of tasks or activities. Activity-based
    descriptions can be easier to use for planning and control at the management level, but task-based descriptions are
    preferred when using them at the practitioner level.
</p>
<p>
    In most cases you should describe at least one sample iteration per phase. Describe the sample iterations as they are
    needed; there is no reason to describe how to work during the Transition phase at the beginning of a project. Start by
    defining how the project will work in the Inception phase.
</p></td>
</tr>
</table>
</div>
<div class="stepHeading">Identify Stakeholders </div>
<div class="stepContent">
<table class="stepTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<td><a id="IdentifyStakeholders" name="IdentifyStakeholders"></a>
<p>
    The role <a class="elementLink" href="./../../rup/roles/rup_stakeholder_1011D446.html" guid="{7A4262EA-AB5B-431E-BB4A-3822FBF7F239}">项目干系人</a> represents all possible stakeholders to a project. You need to
    identify and describe the different types of stakeholders, their needs and responsibilities. Examples of different
    stakeholders are customer representative, user representative, investor, production manager, and buyer.
</p>
<p>
    Describe the different stakeholders and their needs in the development case, in the section "Roles".
</p></td>
</tr>
</table>
</div>
<div class="stepHeading">Map Roles to Job Positions </div>
<div class="stepContent">
<table class="stepTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<td><a id="MapWorkersToJobPositions" name="MapWorkersToJobPositions"></a>
<p>
    In some development organizations there are job positions defined. If these job positions are commonly used and have a
    wide acceptance within the organization, it may be worth doing a mapping between the roles in the NUP, and the job
    positions in the organization. Mapping job positions to roles can make it easier to make people in the organization
    understand how to employ the NUP. The mapping can also help people understand that roles are not job positions, which
    is a common misconception. Document this mapping in the development case, section "Roles".
</p></td>
</tr>
</table>
</div>
<div class="stepHeading">Document the Development Case </div>
<div class="stepContent">
<table class="stepTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<td><a id="DocumentDevelopmentCase" name="DocumentDevelopmentCase"></a> 
<p>
    Describe the development case. See the "Representation Options" section, as well as any associated guidance (e.g.,
    templates and/or examples).
</p></td>
</tr>
</table>
</div>
<div class="stepHeading">Maintain the Development Case </div>
<div class="stepContent">
<table class="stepTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<td><a id="MaintainDevelopmentCase" name="MaintainDevelopmentCase"></a> 
<p>
    Many of the decisions should be made before the project starts. After each iteration in the software-development
    project you should evaluate the process, and reconsider the decisions you have made. If a new version of the underlying
    configuration is released, you need to update the development case.
</p></td>
</tr>
</table>
</div>
</td>
</tr>
</table>
</div>
<div class="sectionHeading">Properties</div>
<div class="sectionContent">
<table class="sectionTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<th class="sectionTableHeading" scope="row" id="property_Multiple Occurrences" abbr="Multiple Occurrences">Multiple Occurrences</th><td class="sectionTableCell" align="left" headers="property_Multiple Occurrences"><img width="20" height="15" alt="" title="" src="./../../images/indent.gif"></td>
</tr>
<tr valign="top">
<th class="sectionTableHeading" scope="row" id="property_Event Driven" abbr="Event Driven">Event Driven</th><td class="sectionTableCell" align="left" headers="property_Event Driven"><img width="20" height="15" alt="" title="" src="./../../images/indent.gif"></td>
</tr>
<tr valign="top">
<th class="sectionTableHeading" scope="row" id="property_Ongoing" abbr="Ongoing">Ongoing</th><td class="sectionTableCell" align="left" headers="property_Ongoing"><img width="20" height="15" alt="" title="" src="./../../images/indent.gif"></td>
</tr>
<tr valign="top">
<th class="sectionTableHeading" scope="row" id="property_Optional" abbr="Optional">Optional</th><td class="sectionTableCell" align="left" headers="property_Optional"><img width="20" height="15" alt="" title="" src="./../../images/indent.gif"></td>
</tr>
<tr valign="top">
<th class="sectionTableHeading" scope="row" id="property_Planned" abbr="Planned">Planned</th><td class="sectionTableCell" align="left" headers="property_Planned"><img width="20" height="15" alt="" title="" src="./../../images/indent.gif"></td>
</tr>
<tr valign="top">
<th class="sectionTableHeading" scope="row" id="property_Repeatable" abbr="Repeatable">Repeatable</th><td class="sectionTableCell" align="left" headers="property_Repeatable"><img width="20" height="15" alt="" title="" src="./../../images/indent.gif"></td>
</tr>
</table>
</div>
<table class="copyright" border="0" cellspacing="0" cellpadding="0">
<tr>
<td class="copyright">Copyright &copy; 2008 版权所有 东软集团股份有限公司&nbsp; 联系邮箱:<a href="mailto:tcoe@neusoft.com">tcoe@neusoft.com</a></td>
</tr>
</table>
</td>
</tr>
</table>
</body>
<script language="JavaScript" type="text/javascript">
					contentPage.onload();
					contentPage.processPage.fixDescriptorLinks();
				</script>
</html>
